atomic-upgrades doc: fix example url to fetch a ref checksum
authorSinny Kumari <sinny@redhat.com>
Wed, 2 Jan 2019 10:33:19 +0000 (16:03 +0530)
committerAtomic Bot <atomic-devel@projectatomic.io>
Wed, 2 Jan 2019 14:26:03 +0000 (14:26 +0000)
Signed-off-by: Sinny Kumari <sinny@redhat.com>
Closes: #1795
Approved by: cgwalters

docs/manual/atomic-upgrades.md

index 9dbe6f8fca5313f0bdbbf9936d5e105ec7bc2b2a..f2c01cc11650d7d6ab42a260bc87fc97a2d4a7f4 100644 (file)
@@ -18,7 +18,7 @@ implements this.
 To begin a simple upgrade, OSTree fetches the contents of the ref from
 the remote server.  Suppose we're tracking a ref named
 `exampleos/buildmaster/x86_64-runtime`.  OSTree fetches the URL
-`http://example.com/repo/refs/exampleos/buildmaster/x86_64-runtime`,
+`http://example.com/repo/refs/heads/exampleos/buildmaster/x86_64-runtime`,
 which contains a SHA256 checksum.  This determines the tree to deploy,
 and `/etc` will be merged from currently booted tree.